Skip to content

[Snyk] Security upgrade com.fasterxml.jackson.datatype:jackson-datatype-jsr310 from 2.10.1 to 2.21.2#202

Open
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-82a34bbfa9457c46d6d9e25d71bf55fc
Open

[Snyk] Security upgrade com.fasterxml.jackson.datatype:jackson-datatype-jsr310 from 2.10.1 to 2.21.2#202
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-82a34bbfa9457c46d6d9e25d71bf55fc

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io bot commented Apr 5, 2026

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

  • samples/server/petstore/spring-mvc-j8-localdatetime/pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue Score Upgrade
high severity Allocation of Resources Without Limits or Throttling
SNYK-JAVA-COMFASTERXMLJACKSONCORE-15907551
  125   com.fasterxml.jackson.datatype:jackson-datatype-jsr310:
2.10.1 -> 2.21.2
No Path Found No Known Exploit

Breaking Change Risk

Merge Risk: Medium

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

@snyk-io
Copy link
Copy Markdown
Author

snyk-io bot commented Apr 5, 2026

Merge Risk: Medium

This upgrade of jackson-datatype-jsr310 from version 2.10.1 to 2.21.2 is a series of minor updates within the same major version. While it consists mostly of bug fixes and improvements, it introduces a behavioral change that requires verification.

Key Changes:

  • Behavioral Change in Duration Serialization: Starting with version 2.10.0, the serialization of java.time.Duration objects now correctly respects the SerializationFeature.WRITE_DURATIONS_AS_TIMESTAMPS setting. Previously, this setting was ignored. If your application enables this feature, Duration objects will now be serialized as a numeric timestamp instead of the default ISO-8601 string format. [11]
  • Stricter Compile-Time Type Checking: Version 2.10.0 introduced stricter generic type assignment checks for mapper.readValue() when used with a TypeReference. This improves type safety and may lead to compile-time errors in code that was previously accepted but incorrect, preventing potential runtime failures. [11]
  • Long-Term Support (LTS): Version 2.21 is designated as an LTS release, which means it will receive security and bug fixes for an extended period. [10]

Recommendation:
Verify any logic that serializes java.time.Duration objects, especially if SerializationFeature.WRITE_DURATIONS_AS_TIMESTAMPS is enabled, to ensure the change in output format does not break downstream consumers. Review any new compile-time errors related to TypeReference usage.

Source: Jackson 2.10 Release Notes

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@snyk-io
Copy link
Copy Markdown
Author

snyk-io bot commented Apr 5, 2026

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants